Skip to content

Take __CPROVER_allocated_memory regions into account for --bounds-check #4256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 22, 2019

Conversation

tautschnig
Copy link
Collaborator

We already took these into account for --pointer-check. Do the same for
--bounds-check.

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

We already took these into account for --pointer-check. Do the same for
--bounds-check.
@tautschnig tautschnig self-assigned this Feb 22, 2019
@tautschnig tautschnig merged commit 744c6f3 into diffblue:develop Feb 22, 2019
@tautschnig tautschnig deleted the allocated-bounds branch February 22, 2019 18:32
@tautschnig tautschnig restored the allocated-bounds branch December 27, 2020 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants